This repository has been archived by the owner on Apr 28, 2023. It is now read-only.
Continuous Deployment on Large Ruby Teams #79
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your proposal. Unfortunately, due to the high number of excellent proposals, our panel has not been able to include this talk at this stage. Should this situation change, we will contact you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated deployments of applications that are made up of a large number of services (in our case 20) can be hard, especially when there's a large team building them.
Here we discuss various branching strategies, ways to share code between the services, a continuous integration server performing unit tests on individual services & integration tests across all services, preparation of packages and automatic deployment to staging and production.
We will talk about how a CI pipeline, private gem servers, puppet scripts and a mouse-click come together to give us the one-click deployment everyone dreams of.